Test: Update component tests for Apollo #71
Merged
+226
−13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaces #67, which got stuck. Same commits (by @jonatsm), merged with the latest
main.Closes #43
What changed
SubmitSightingPage.tsx).npm run testnow runs the frontend (Vitest) and backend tests once, as CI does.tsx. Running the.tstest file directly gaveERR_UNKNOWN_FILE_EXTENSIONon some Node versions. The same fix is inb1972db.AGENTS.mdupdated to match the new test commands.Review history from #67
ERR_UNKNOWN_FILE_EXTENSIONwhen runningnpm testand asked for the backend test script to run throughtsx.b1972db, and @asgeija confirmed thatnpm testworks.main.The commits are unchanged apart from the merge with
main, so this needs a fresh approval but should not need new code review.Testing
npm run lintnpm run testComponent tests mock Apollo, so no backend or database is needed.
AI usage
Claude Code was used to copy this PR onto a new branch. The code changes are the original work from #67.